home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1995.02
/
000162_taob@ibms.sinica.edu.tw_Wed Mar 1 05:37:39 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-28
|
8KB
Received: from ibms.sinica.edu.tw by cs.umb.edu with SMTP id AA28818
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Tue, 28 Feb 1995 14:56:17 -0500
Received: by ibms.sinica.edu.tw (4.1/SMI-4.1)
id AA05679; Tue, 28 Feb 95 21:37:39 CST
Message-Id: <9502281337.AA05679@ibms.sinica.edu.tw>
Subject: Re: Problems compiling web2c-6.1 on FreeBSD 2.0
To: tex-k@cs.umb.edu
Date: Tue, 28 Feb 1995 21:37:39 +0800 (WST)
Cc: taob@io.org
In-Reply-To: <9502261911.AA18589@ibms.sinica.edu.tw> from "Brian Tao" at Feb 27, 95 03:11:44 am
From: taob@io.org (Brian Tao)
Reply-To: taob@io.org (Brian Tao)
X-Mailer: ELM [version 2.4 PL13]
Content-Type: text
Content-Length: 7630
Thank you all (Karl Berry, Timothy Murphy, Philippe Charnier and
Dan Karron) for a prompt response. It turns out that the person who
was called in to install TeX before me decided to define TEXFONTS,
TEXINPUTS, etc. in /etc/csh.cshrc rather than in his own personal
.cshrc. Even though the paths were correct, he did not use the //
notation, and I suspect that is why none of the files were found.
As suggested, I followed the instructions in web2c.kpathsea-2.6.help
and merged the web-6.1.tar.gz, web2c-6.1.tar.gz, dvipsk-5.58f.tar.gz
and xdvik-18f.tar.gz archives into a single directory. I applied the
patches and made a few changes for FreeBSD as outlined in the various
INSTALL files. SMART_PUTENV must be defined for FreeBSD, but it
appears the change should be made in the acconfig.h file before
Configure or make is invoked. I don't the acconfig.h file is
documented anywhere. Doing a "./configure" from the top-level
directory does not auto-detect this. Editing c-auto.h after I had
gone throug the make cycle once and rebuilding did not appear to work
either. The same problem occurred with NO_FOIL_X_WCHAR_T (also needed
by FreeBSD).
Anyhow, I was able to complete the 'make -k all' and then 'make
install'. To test, I attempted to run some of the LaTeX documentation
through 'latex' to see if I could get readable .dvi files out of them.
At first it was complaining that it could find the default format
file, but merging my texmf and texmf-orig directories solved the
problem. texmf-orig contained the latex2e files, and I moved them
out of the way before trying to build TeX. There were many warnings,
but I am told this is fairly normal (and it tells you to rerun latex
anyway, sometimes more than once).
When I used xdvi to preview the .dvi file, I received several
messages about MakeTeXPK generating fonts, but xdvi not being able
to find them:
> # xdvi usrguide
> kpathsea: Running MakeTeXPK cmss9 300 300 1+0/300
> kpathsea: Appending font creation commands to missfont.log.
> xdvi: Can't find font cmss9; using cmr10 instead at 300 dpi.
> kpathsea: Running MakeTeXPK cmmib10 360 300 magstep\(1.0\)
> xdvi: Can't find font cmmib10 at 360 dpi; using 300 dpi instead.
> kpathsea: Running MakeTeXPK cmbx12 360 300 magstep\(1.0\)
> xdvi: Can't find font cmbx12 at 360 dpi; using 300 dpi instead.
> kpathsea: Running MakeTeXPK cmmi12 432 300 magstep\(2.0\)
> xdvi: Can't find font cmmi12 at 432 dpi; using 300 dpi instead.
> kpathsea: Running MakeTeXPK line10 300 300 1+0/300
> xdvi: Can't find font line10; using cmr10 instead at 300 dpi.
> Note: overstrike characters may be incorrect.
It looks like MakeTeXPK is saving the fonts into /tmp/pk. Isn't
this a bad choice for a default location? Most systems clear out /tmp
on a reboot. Wouldn't /usr/local/lib/texmf/fonts/pk make more sense?
When I tried a 'locate' on "cmmi12", I find the following files:
> # locate cmmi12
> /usr/local/lib/texmf-orig/fonts/tfm/cmmi12.tfm
> /usr/local/lib/texmf-orig/mf/cmmi12.mf
> /usr/local/lib/texmf/fonts/public/cm/pk/cx/cmmi12.300pk
> /usr/local/lib/texmf/fonts/public/cm/src/cmmi12.mf
> /usr/local/lib/texmf/fonts/public/cm/tfm/cmmi12.tfm
> /usr/X11R6/lib/texmf/fonts/pk/cmmi12.300pk
> /usr/X11R6/lib/texmf/fonts/pk/cmmi12.328pk
> /usr/X11R6/lib/texmf/fonts/pk/cmmi12.329pk
> /usr/X11R6/lib/texmf/fonts/pk/cmmi12.360pk
I don't recall anything in the installation notes about placing
files in /usr/X11R6/lib/texmf, so I'll assume that those files were
created by my predecessor. Where did he get those pk/ fonts? I don't
see then in lib.tar.gz nor in pk300.zip. Moving the fonts/pk/
directory into /usr/local/lib/texmf/fonts caused all but one of the
errors to go away:
> # xdvi usrguide
> kpathsea: Running MakeTeXPK cmmi12 432 300 magstep\(2.0\)
> kpathsea: Appending font creation commands to missfont.log.
> xdvi: Can't find font cmmi12 at 432 dpi; using 300 dpi instead.
> Note: overstrike characters may be incorrect.
Upon reading the man page for mf(1) to see which environment
variables I should set, I found that the default values had not be
replaced by the proper values:
> MFINPUTS Search path for input and openin files.
> Default:
> @DEFAULT_MF_PATH@
>
> MFBASES Search path for base files. Default:
> @DEFAULT_BASE_PATH@
[etc.]
The web2c/man/ directory that contains the manual page sources had
both the original .man and the substituted .1 files. But looking in
sedscript, I could not find any reference to @DEFAULT_MF_PATH@,
@DEFAULT_BASE_PATH@ and several others. Did I forget to edit a file
somewhere that contains the definition of these paths? Is this
related to the problem with xdvi not finding the correct fonts? The
file looks fine in xdvi though.
Last one. ;-) Running 'dvips' on the usrguide.dvi produces
several more errors:
> # dvips -f < usrguide.dvi > usrguide.ps
> This is dvipsk 5.58f Copyright 1986, 1994 Radical Eye Software
> ' TeX output 1995.02.28:1710' ->
> kpathsea: Running MakeTeXPK cmr17 600 600 1+0/600 ljfour
> kpathsea: Appending font creation commands to missfont.log.
> dvips: Font cmr17 not found, characters will be left blank.
> kpathsea: Running MakeTeXPK cmr12 600 600 1+0/600 ljfour
> dvips: Font cmr12 not found, characters will be left blank.
> kpathsea: Running MakeTeXPK cmmi12 864 600 magstep\(2.0\) ljfour
> dvips: Font cmmi12 not found, characters will be left blank.
[...]
> <texc.pro>. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
> [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26]
> [27] [28] [29] [30]
This goes one for another 18 fonts or so, and the produced
PostScript file is predictably empty. BTW, I assume the "ljfour" at
the end of the kpathsea lines refer to a LaserJet 4. How did it know
I had one? :) Where does it find this information? I went to look
in the dvips man page, but it warns that the info contained therein is
out of date, and that I should consult the info pages instead.
Unfortunately, I haven't set up texinfo here yet, so dvips will have
to wait.
Are all my problems with fonts related to single bad config file?
Or do I have to slog through the configs for xdvi and dvips and look
for anything to do with pathnames? I have not moved any files around
from their suggested places, in the hopes that I could avoid messing
around with config.h's and Makefiles and their ilk.
Now that I'm very close to having a fully-functional TeX/LaTeX/
MetaFont/xdvi/dvips package, would it be too much to ask for a
"starter kit" of this stuff? That is, a single tar.gz file that
contains everything in one great big package. A new LaTeX user
can then unpack it into a single directory, type './configure' and
then type 'make' to compile everything, then 'make install' to install
all the binaries, fonts, documentation and other support files into
standard locations. While I was struggling with TeX, I was able to
build and install GhostScript 3.12 with JPEG extensions and GNUemacs
19.28 by doing exactly the above. Both are large, complex packages as
well. Are there any plans for this? The entire web2c/kpathsea package
has given me the most difficulty out of any package I have installed on
any UNIX platform. I don't intend to flame or belittle the excellent
work that has gone into the entire TeX system, but I'd really like to
see the installation procedure for first-time users improved.
Having said all that, I look forward to learning the TeX language.
;-)